Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Always have WSCA manage registry, enable distribution (#27) #60

Merged
merged 1 commit into from
Oct 12, 2024

Conversation

sander
Copy link
Owner

@sander sander commented Sep 14, 2024

After further discussion it seems there is already consensus with the Expert Group that key association is fully managed by a WSCA. It seems like we can achieve the same functional and certification needs by adopting this model, and potentially deploying it in a distributed way with an internal WSCA agent and an external and possibly remote WSCA service.

After merging this, the HDK presentation needs to be updated accordingly.

After further discussion it seems there is already consensus
with the Expert Group that key association is fully managed
by a WSCA. It seems like we can achieve the same functional
and certification needs by adopting this model, and potentially
deploying it in a distributed way with an internal WSCA agent
and an external and possibly remote WSCA service.
@sander
Copy link
Owner Author

sander commented Sep 16, 2024

Preview: see feat/distributed-wsca at https://sander.github.io/hierarchical-deterministic-keys/

@sander sander merged commit bc2865d into main Oct 12, 2024
2 checks passed
@sander sander deleted the feat/distributed-wsca branch October 12, 2024 08:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

1 participant